-
Notifications
You must be signed in to change notification settings - Fork 593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(optimizer): ensure column name unique when create MV #1363
Conversation
…make_column_name_unique
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Is #
valid in column name in Postgres?
I am not sure, and we can change it anytime |
Codecov Report
@@ Coverage Diff @@
## main #1363 +/- ##
=========================================
Coverage 70.08% 70.08%
Complexity 2766 2766
=========================================
Files 1030 1030
Lines 89098 89155 +57
Branches 1790 1790
=========================================
+ Hits 62442 62482 +40
- Misses 25765 25782 +17
Partials 891 891
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. BTW, we also need to fix the panic column name dup assert in table_catalog.rs L115?
pub fn gen_row_id_column_name(idx: usize) -> String { | ||
ROWID_PREFIX.to_string() + "#" + &idx.to_string() | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why we need this? I guess index row_id is always 0 or 1? And is it only used in explain display?
What's changed and what's your intention?
PLEASE DO NOT LEAVE THIS EMPTY !!!
Checklist
Refer to a related PR or issue link (optional)
#1331